Using physical gestures to initiate call transfers between devices

ABSTRACT

Various technologies described herein pertain to using detected physical gestures to cause calls to transfer between client devices. A physical gesture between a first client device and a second client device can be detected (e.g., utilizing the first client device, the second client device, a disparate client-side device, a server, etc.). The first client device participates in a call, while the second client device is not participating in the call at a time of the detection of the physical gesture. Responsive to detection of the physical gesture, participation of the second client device in the call can be initiated. Participation of the second client device in the call can be initiated by causing the call to transfer from the first client device to the second client device or causing the second client device to join the call while the first client device continues to participate in the call.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.13/918,530, filed on Jun. 14, 2013, and entitled “USING PHYSICALGESTURES TO INITIATE CALL TRANSFERS BETWEEN DEVICES”, the entirety ofwhich is incorporated herein by reference.

BACKGROUND

Conventional approaches for transferring a call from a first caller to asecond caller or conferencing multiple callers into the call oftentimesinvolve performance of a complex sequence of steps. For instance, ifattempting to conference more than one caller into a call, a usercommonly places a first caller on hold, dials a second caller, and thenconferences the first and second callers together on the call. Toaccomplish the foregoing, the user may need to have knowledge of thesequence of steps to enable carrying out such action. Thus, the user mayneed to know to press a particular button to place the first caller onhold, know the number of the second caller who is being added to theconference call, and then know to press another button to join the twocalls together.

According to another illustration, a user may call a group of friendswith whom she desires to talk. The user may call a particular friendfrom the group and begin to talk to that person. Upon finishing theconversation with that friend, the user may wish to talk to a nextfriend in the group. A common approach for enabling the user to talk tothe next friend is for the first friend to hand her phone over to thenext friend. Alternatively, a sequence of steps can be taken to transferthe call from the phone of the first friend to the phone of the secondfriend. However, similar to above, such approach may require priorknowledge of how to accomplish the transfer of the call.

SUMMARY

Described herein are various technologies that pertain to using detectedphysical gestures to cause calls to transfer between client devices. Aphysical gesture between a first client device and a second clientdevice can be detected. The first client device can be participating ina call at a time of detection of the physical gesture. Moreover, thesecond client device is not participating in the call at the time of thedetection of the physical gesture. The physical gesture can be detectedutilizing the first client device, the second client device, a disparateclient-side device (e.g., a sensor, etc.), a server, or the like.Responsive to the detection of the physical gesture, participation ofthe second client device in the call can be initiated. For example,participation of the second client device in the call can be initiatedby causing the call to transfer from the first client device to thesecond client device (e.g., a transfer action). According to anotherexample, participation of the second client device in the call can beinitiated by causing the second client device to join the call while thefirst client device continues to participate in the call (e.g., aconference action).

In accordance with various embodiments, different types of physicalgestures can be detected. For instance, the physical gesture between thefirst client device and the second client device can be a tap betweenthe first client device and the second client device. According toanother example, the physical gesture can be a motion of the secondclient device relative to the first client device and/or a motion of thefirst client device relative to the second client device. However, othertypes of physical gestures of the first client device and/or the secondclient device are intended to fall within the scope of the heretoappended claims. Moreover, according to other embodiments, it iscontemplated that the physical gesture can be between an agent of thefirst client device and the second client device, between the firstclient device and an agent of the second client device, or between theagent of the first client device and the agent of the second clientdevice.

Various embodiments set forth herein pertain to routing a call. Forinstance, data packets that are part of the call can be transmitted tothe first client device. A request to route the data packets that arepart of the call to a second client device can thereafter be received.The request can be responsive to a detected physical gesture between thefirst client device and the second client device. The data packets thatare part of the call are not routed to the second client device prior toreceipt of the request. Moreover, whether to grant the request or denythe request can be determined. Further, responsive to a determination togrant the request, the data packets that are part of the call can betransmitted to the second client device. The data packets that are partof the call may or may not continue to be transmitted to the firstclient device upon determining to grant the request (e.g., dependingupon whether the call is transferred or a conference call isestablished).

The above summary presents a simplified summary in order to provide abasic understanding of some aspects of the systems and/or methodsdiscussed herein. This summary is not an extensive overview of thesystems and/or methods discussed herein. It is not intended to identifykey/critical elements or to delineate the scope of such systems and/ormethods. Its sole purpose is to present some concepts in a simplifiedform as a prelude to the more detailed description that is presentedlater.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a functional block diagram of an exemplary systemthat utilizes a physical gesture to initiate a call transfer orconference call between client devices.

FIGS. 2-4 illustrate various exemplary scenarios where a physicalgesture initiates a call transfer or a conference call between theclient devices of FIG. 1

FIG. 5 illustrates a functional block diagram of an exemplary systemthat utilizes different types of physical gestures to identify differenttypes of actions pertaining to a call.

FIGS. 6-8 illustrate various examples of different types of taps betweenclient devices.

FIG. 9 illustrates a functional block diagram of an exemplary systemthat routes a call to a client device responsive to a physical gesturebetween the client device and a differing client device.

FIG. 10 illustrates a functional block diagram of an exemplary systemthat employs physical gestures to initiate transferring calls betweenclient devices.

FIG. 11 illustrates a functional block diagram of an exemplary systemthat transfers calls responsive to detected physical gestures betweenclient devices.

FIG. 12 illustrates a functional block diagram of an exemplary systemthat sources a call from a first client device to a second client deviceresponsive to detection of a physical gesture.

FIG. 13 illustrates a functional block diagram of an exemplary systemthat transfers calls responsive to a physical gesture based uponcapabilities of client devices.

FIG. 14 illustrates a functional block diagram of an exemplary systemthat routes a call to client device(s) from a call server.

FIG. 15 illustrates a functional block diagram of an exemplary systemthat employs agents with the client devices.

FIG. 16 illustrates a functional block diagram of an exemplary systemthat employs a sensor to detect a physical gesture between clientdevices.

FIG. 17 is a flow diagram that illustrates an exemplary methodology ofjoining a client device to an existing call.

FIG. 18 is a flow diagram that illustrates an exemplary methodology ofrouting a call.

FIG. 19 is a flow diagram that illustrates another exemplary methodologyof routing a call.

FIG. 20 illustrates an exemplary computing device.

DETAILED DESCRIPTION

Various technologies pertaining to utilizing a physical gesture toinitiate a call transfer or conference call between client devices arenow described with reference to the drawings, wherein like referencenumerals are used to refer to like elements throughout. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide a thorough understanding of one or moreaspects. It may be evident, however, that such aspect(s) may bepracticed without these specific details. In other instances, well-knownstructures and devices are shown in block diagram form in order tofacilitate describing one or more aspects. Further, it is to beunderstood that functionality that is described as being carried out bycertain system components may be performed by multiple components.Similarly, for instance, a component may be configured to performfunctionality that is described as being carried out by multiplecomponents.

Moreover, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom the context, the phrase “X employs A or B” is intended to mean anyof the natural inclusive permutations. That is, the phrase “X employs Aor B” is satisfied by any of the following instances: X employs A; Xemploys B; or X employs both A and B. In addition, the articles “a” and“an” as used in this application and the appended claims shouldgenerally be construed to mean “one or more” unless specified otherwiseor clear from the context to be directed to a singular form.

As set forth herein, a physical gesture between client devices can bedetected; responsive to the detected physical gesture, a call to one ofthe client devices can be re-routed to the other client device. Forexample, a user may tap her mobile device to a conference phone in aconference room when leaving the conference room (e.g., to cause aconference call to be transferred from the conference phone to themobile device, to join the conference call while the conference phoneremains on the conference call, etc.). According to another example, auser may tap his car with his mobile device when exiting the car (e.g.,to cause a call in which an integrated phone of the car is participatingto transfer to the mobile device, to join the call while the integratedphone continues to participate in the call, etc.). Moreover, techniquesset forth herein support group calling or transferring a call betweenclient devices of friends; for instance, rather than passing a mobiledevice around a room, users can tap mobile devices together to transferthe call, form a conference call, etc. While tapping is described in theforegoing exemplary scenarios, it is contemplated that substantially anytype of physical gesture is intended to fall within the scope of thehereto appended claims.

Referring now to the drawings, FIG. 1 illustrates a system 100 thatutilizes a physical gesture to initiate a call transfer or conferencecall between client devices. The system 100 includes a client device A102 and a client device B 104. Although not shown, it is to beappreciated that the system 100 can include more than two clientdevices, which can each be substantially similar to the client device A102 and/or the client device B 104. Moreover, although not shown, it iscontemplated that the system 100 can include a network over which theclient device A 102 and/or the client device B 104 send and/or receivepackets, signals, data, information, etc. pertaining to a call 106. Itis to be appreciated that two or more parties (e.g., the client device A102, the client device B 104, disparate client device(s) (not shown),etc.) can participate in the call 106.

The client device A 102 and the client device B 104 can be substantiallyany type of client device that can participate in the call 106. Examplesof device types include, but are not limited to, mobile devices (e.g.,smartphones, feature phones, other types of mobile phones, tabletcomputers, handheld computers, personal digital assistants (PDAs),portable gaming devices, wearable computers, etc.), personal computers,laptop computers, phones, conference phones, in-vehicle communicationsand infotainment systems (e.g., including integrated phones, etc.),televisions, gaming consoles, media centers, or the like.

The client device A 102 includes a communication component 108 that cansend and/or receive packets, signals, data, information, etc. that arepart of the call 106. As described in many of the examples set forthherein, the client device A 102 can participate in the call 106 via afirst connection; thus, the communication component 108 can exchangepackets, signals, data, information, etc. that are part of the call 106with one or more disparate client devices (not shown) via the firstconnection. It is to be appreciated that the first connection can beestablished in substantially any manner. For example, the client deviceA 102 can initiate the call 106, which can cause the first connection tobe established. By way of another example, a disparate client device(other than the client device A 102) can initiate the call 106 to theclient device A 102, which can cause the first connection to beestablished. Pursuant to a further example, the call 106 can be ongoingwhen the client device A 102 joins (e.g., via transferring orconferencing as described herein); upon the client device A 102 joiningthe call 106, the first connection can be established.

In accordance with many of the exemplary scenarios described herein, theclient device A 102 can participate in the call 106 via the firstconnection while the client device B 104 is not participating in thecall 106 at a given time. Subsequent to the given time, a physicalgesture can be detected. Responsive to detection of the physicalgesture, a second connection can be established whereby the clientdevice B 104 can participate in the call 106 (e.g., with or without theclient device A 102 participating in the call 106 via the firstconnection to the call 106).

The client device A 102 can further include a sensing component 110 thatcan detect a physical gesture between the client device B 104 and theclient device A 102. The sensing component 110 can detect substantiallyany type of physical gesture between the client device B 104 and theclient device A 102. For example, the sensing component 110 can detect atap between the client device B 104 and the client device A 102.According to another example, the sensing component 110 can detect amotion of the client device B 104 relative to the client device A 102and/or a motion of the client device A 102 relative to the client deviceB 104. It is to be appreciated, however, that other types of physicalgestures between the client device B 104 and the client device A 102 canbe detected by the sensing component 110. Yet, a physical gesturebetween the client device B 104 and the client device A 102 as describedherein differs from activation of a button of the client device B 104and/or the client device A 102; for instance, a physical gesture asdescribed herein is not intended to include activation of a touchscreenbutton (e.g., a button displayed on a touchscreen of the client device A102 to transfer the call to the client device B 104, etc.).

It is contemplated that various forms of input can be analyzed by thesensing component 110 to detect the physical gesture between the clientdevice B 104 and the client device A 102. For example, the sensingcomponent 110 can employ near field communication (NFC) to detect a tapbetween the client device B 104 and the client device A 102. Inaccordance with another example, the sensing component 110 can detectthe physical gesture based on strength of a signal received from theclient device B 104. By way of another example, the sensing component110 can utilize output of an accelerometer and/or a gyroscope includedin the client device A 102 and/or the client device B 104 to detect thephysical gesture. Moreover, the sensing component 110 can utilizelocation information based on external signals, such as Wi-Fi location,Global Positioning System (GPS), Assisted GPS (AGPS), etc., to detectthe physical gesture. In accordance with yet another example, thesensing component 110 can employ output of a camera (e.g., motionsensor, etc.) to detect the physical gesture between the client device B104 and the client device A 102. Further, it is to be appreciated that acombination of the foregoing examples can be employed by the sensingcomponent 110 to detect the physical gesture between the client device B104 and the client device A 102.

The client device A 102 can further include an access instigationcomponent 112 that can initiate participation of the client device B 104in the call 106 from the client device A 102 responsive to the detectionof the physical gesture by the sensing component 110. The accessinstigation component 112 can cause the second connection to beestablished, for instance. According to an example, the accessinstigation component 112 can cause the call 106 to transfer from theclient device A 102 to the client device B 104 responsive to thephysical gesture being detected by the sensing component 110. Thus, theaccess instigation component 112 can initiate the participation of theclient device B 104 in the call 106 by causing the call 106 to betransferred from the client device A 102 to the client device B 104. Byway of another example, the access instigation component 112 can causethe client device B 104 to join the call 106 responsive to detection ofthe physical gesture by the sensing component 110. Following thisexample, the access instigation component 112 can initiate theparticipation of the client device B 104 in the call 106 by causing theclient device B 104 to join the call 106 while the client device A 102continues to participate in the call 106.

Moreover, the client device B 104 can include a communication component114, which can be substantially similar to the communication component108 of the client device A 102. Upon establishment of the secondconnection, the communication component 114 can exchange packets,signals, data, information, etc. that are part of the call 106 with oneor more disparate client devices (not shown) via the second connection.Moreover, if the client device A 102 continues to participate in thecall 106 after the client device B 104 joins, then the communicationcomponent 114 can additionally exchange packets, signals, data,information, etc. that are part of the call 106 with the client device A102.

Although not shown, it is to be appreciated that the client device B 104can be participating in a disparate call (e.g., a call other than thecall 106) prior to establishment of the second connection for the call106. Pursuant to this exemplary scenario, the call 106 and the disparatecall can be combined upon establishment of the second connection for thecall 106, for example. Alternatively, the client device B 104 candisconnect from the disparate call when establishing the secondconnection for the call 106.

According to various examples, different types of physical gestures canbe detected by the sensing component 110. Different types of physicalgestures between the client device A 102 and the client device B 104 cancorrespond to differing types of actions pertaining to the call 106. Forexample, a first physical gesture type can correspond to transferringthe call 106 from the client device A 102 to the client device B 104(referred to herein as a transfer action), whereas a second physicalgesture type can correspond to joining the client device B 104 to thecall 106 while the client device A 102 continues to participate in thecall 106 (referred to herein as a conference action). Moreover,different types of physical gestures can differentiate between promptingor not prompting a user to confirm an action pertaining to the call. Forinstance, a particular physical gesture type can cause a prompt to bedisplayed on a display screen of the client device A 102 that solicitsuser input pertaining to whether to transfer the call 106 to clientdevice B 104 (e.g., transfer can occur or not occur responsive to theuser input) whereas a different physical gesture type can cause the call106 to transfer to the client device B 104 without prompting for userconfirmation. Similarly, differing physical gesture types can cause aprompt for user confirmation to be displayed or not for a conferenceaction.

Moreover, the sensing component 110 can discern an identifier of theclient device B 104 when the physical gesture between the client deviceB 104 and the client device A 102 is detected. For instance, theidentifier can be utilized by the access instigation component 112 toinitiate the participation of the client device B 104 in the call 106from the client device A 102. According to an example, the identifiercan be a phone identifier included in an NFC record; however, theclaimed subject matter is not so limited.

While many of the examples set forth herein describe that the clientdevice A 102 includes the sensing component 110 and the accessinstigation component 112, it is contemplated that the client device B104 and/or a disparate client-side device can additionally oralternatively include the sensing component 110 and/or the accessinstigation component 112. For example, although not shown, the clientdevice B 104 can include the sensing component 110 and/or the accessinstigation component 112. According to a further example, a disparateclient-side device (e.g., a sensor such as a camera, a differing clientdevice other than the client device A 102 or the client device B 104,etc.) separate from the client device A 102 and the client device B 104can include the sensing component 110 and/or the access instigationcomponent 112. Thus, the examples set forth herein (where the clientdevice A 102 includes the sensing component 110 and the accessinstigation component 112) can be extended to scenarios where the clientdevice B 104, the disparate client-side device separate from the clientdevice A 102 and the client device B 104, or a combination thereofadditionally or alternatively include the sensing component 110 and/orthe access instigation component 112.

According to another example, it is contemplated that a server (orplurality of servers) can additionally or alternatively include thesensing component 110 and/or the access instigation component 112. It isto be appreciated the server can be a call server (e.g., a call server1002 of FIG. 10) or a disparate server in a network. Following thisexample, the sensing component 110 of the server can collocate theclient device A 102 and the client device B 104 within a particulargeographic area (e.g., based on Wi-Fi, GPS, AGPS, etc.) and then detectthe physical gesture based on data received from the client device A 102and the client device B 104 (e.g., based on data from respectiveaccelerometers of the client device A 102 and the client device B 104indicative of taps within a period of time, etc.). Based upon thedetected physical gesture, the access instigation component 112 caninitiate the participation of the client device B 104 in the call.Accordingly, the examples set forth herein (where the client device A102 includes the sensing component 110 and the access instigationcomponent 112) can be extended to scenarios where the serveradditionally or alternatively includes the sensing component 110 and/orthe access instigation component 112.

FIGS. 2-4 depict various exemplary scenarios where a physical gestureinitiates a call transfer or a conference call between the client deviceA 102 and the client device B 104 of FIG. 1. FIGS. 2-4 show the clientdevice A 102 and the client device B 104 as mobile devices; yet, asdescribed herein, it is contemplated that the client device A 102 and/orthe client device B 104 can be a disparate type of client device otherthan a mobile device.

With reference to FIG. 2, illustrated is an exemplary scenario where theclient device B 104 is joined to a call responsive to a physicalgesture. As shown at 200, the client device A 102 is participating inthe call while the client device B 104 is not participating in the call.At 202, a physical gesture occurs between the client device A 102 andthe client device B 104. At 204, both the client device A 102 and theclient device B 104 are participating in the call subsequent to thephysical gesture. Thus, in accordance with the exemplary scenario ofFIG. 2, responsive to the physical gesture, the client device B 104 canjoin the call while the client device A 102 continues to participate inthe call.

Turning to FIG. 3, illustrated is an exemplary scenario where a call istransferred between client devices. At 300, the client device A 102 isparticipating in the call while the client device B 104 is notparticipating in the call. Thereafter, at 302, a physical gesturebetween the client device A 102 and the client device B 104 occurs. At304, responsive to the physical gesture, the call is transferred fromthe client device A 102 to the client device B 104. Accordingly,subsequent to the physical gesture, the client device B 104 participatesin the call while the client device A 102 no longer participates in thecall.

Turning to FIG. 4, illustrated is another exemplary scenario where theclient device B 104 is joined to a call responsive to a physicalgesture. At 400, the client device A 102 is participating in the callwhile the client device B 104 is not participating in the call.Responsive to a physical gesture between the client device A 102 and theclient device B 104 at 402, the client device A 102 can display a prompton a display screen at 404. The prompt can solicit user input concerningwhether or not to allow the client device B 104 to join the call.Moreover, at 404, the client device B 104 can indicate that such deviceis connecting to the call. Responsive to YES being selected on theclient device A 102 at 406, the client device A 102 and the clientdevice B 104 both participate in the call at 408. Alternatively, if NOis selected on the client device A 102, then the attempt to join theclient device B 104 can be discontinued (e.g., the client device A 102can continue to participate in the call and the client device B 104 cancontinue to not participate in the call).

Further, it is contemplated that other types of user input can indicateYES or NO being selected on the client device A 102. For instance, theclient device A 102 can detect whether or not to allow the client deviceB 104 to join responsive to a detected gesture of a user of the clientdevice A 102, voice input of the user of the client device A 102, or thelike.

Moreover, although not shown, it is contemplated that a “Join Call”dialog can be displayed on a display screen of the client device B 104at 404. Such dialog can solicit user input concerning whether to jointhe call with the client device B 104. Similar types of user input asset forth above with respect to the client device A 102 can be utilizedto indicate YES or NO being selected on the client device B 104.

Now turning to FIG. 5, illustrated is a system 500 that utilizesdifferent types of physical gestures to identify different types ofactions pertaining to a call. Again, the system 500 includes the clientdevice A 102 and the client device B 104, where the client device A 102is participating in the call and the client device B 104 is notparticipating in the call prior to detection of a physical gesture(e.g., by the sensing component 110).

The client device A 102 can further include a type evaluation component502 that identifies a gesture type of the physical gesture detected bythe sensing component 110 from a set of possible gesture types. Thepossible gesture types in the set correspond to differing respectiveactions pertaining to the call. Moreover, the access instigationcomponent 112 can cause a particular action pertaining to the callcorresponding to the gesture type detected by the type evaluationcomponent 502 responsive to the detection of the physical gesture by thesensing component 110 and the identification of the gesture type by thetype evaluation component 502.

According to an example, the physical gesture can be a tap; thus, thetype evaluation component 502 can identify a tap type of the tap from aset of possible tap types. The possible tap types in the set cancorrespond to differing respective actions pertaining to the call.Further, the access instigation component 112 can cause a particularaction pertaining to the call corresponding to the tap type responsiveto the detection of the tap and the identification of the tap type.However, it is contemplated that other types of physical gestures otherthan taps are intended to fall within the scope of the hereto appendedclaims.

Again, reference is made to the example where the physical gesture is atap. By way of illustration, a first possible tap type can correspond toa transfer action, where the call is transferred from the client deviceA 102 to the client device B 104. Moreover, a second possible tap typecan correspond to a conference action, where the client device B 104 isjoined to the call while the client device A 102 continues toparticipate in the call. However, other types of actions pertaining tothe call are intended to fall within the scope of the hereto appendedclaims (e.g., automatic confirmation of a transfer action as shown inFIG. 3, automatic confirmation of a conference action as shown in FIG.2, a transfer action that includes prompting for confirmation, aconference action that includes prompting for confirmation as shown inFIG. 4, etc.).

Continued reference is made to the exemplary scenario where the physicalgesture is a tap. The type evaluation component 502 can identify the taptype of the tap as a function of a location on a housing of the clientdevice A 102 at which the tap is detected (e.g., tap point, etc.), anorientation of the client device B 104 with respect to the client deviceA 102 during the tap, a time duration of the tap (e.g., tap and hold,etc.), a number of occurrences of the tap (e.g., single tap, double tap,etc.), a combination thereof, and so forth. Thus, tap actions can havemultiple definitions depending on context or policy. For instance, adouble tap may be utilized to transfer a call from the client device A102 to the client device B 104 (e.g., a double tap can correspond to atransfer action), whereas a single tap can be utilized to join theclient device B 104 to the call while the client device A 102 continuesto participate in the call (e.g., a single tap can correspond to aconference action). By way of another example, a double tap can be anautomatic confirmation of acceptance for a transfer action, whereas asingle tap can correspond to a transfer action that includes promptingfor confirmation from a user of the client device A 102 (e.g.,presenting a selectable button on a display screen of the client deviceA 102 to accept or reject transferring the call to the client device B104).

FIGS. 6-8 illustrate various examples of different types of taps betweenthe client device A 102 and the client device B 104. Again, the clientdevice A 102 and the client device B 104 are depicted as mobile devices;yet, as described herein, it is to be appreciated that the client deviceA 102 and/or the client device B 104 can be a disparate type of clientdevice other than a mobile device.

Turning to FIG. 6, illustrated is an example where a tap type isdetermined based upon a location of a tap on a housing of the clientdevice A 102. A tap between the client device A 102 and the clientdevice B 104 at a location 600 on the housing of the client device A 102can correspond to a first tap type. Moreover, a tap between the clientdevice A 102 and the client device B 104 at a location 602 on thehousing of the client device A 102 can correspond to a second tap type.Thus, the client device A 102 can include different tap points (e.g.,the location 600 versus the location 602) such that a tap at thelocation 600 on the housing of the client device A 102 can cause a firstaction pertaining to a call and a tap at the location 602 on the housingof the client device B 104 can cause a differing second actionpertaining to the call.

The client device A 102 can employ various techniques to detect whethera tap is at the location 600 or the location 602. For instance, theclient device A 102 can include two NFC chips (e.g., one positioned ator near the location 600 and the other positioned at or near thelocation 602). By way of another example, the client device A 102 candetermine whether the tap is at the location 600 or the location 602based upon signal strength (e.g., an NFC chip can be positioned at ornear either the location 600 or the location 602). However, it is to beappreciated that other techniques for determining the location of thetap on the housing of the client device A 102 are intended to fallwithin the scope of the hereto appended claims.

While FIG. 6 illustrates two locations on the housing of the clientdevice A 102 being utilized to distinguish between tap types, it is tobe appreciated that substantially any number of locations on the housingof the client device A 102 can be employed. Moreover, it is to beappreciated that the locations need not be at a top and a bottom of theclient device A 102; rather, substantially any other locations on thehousing can be employed (e.g., front versus back, side versus side,first corner versus second corner, etc.).

Moreover, it is to be appreciated that locations on the housing of theclient device B 104 can additionally or alternatively be associated withdiffering tap types. According to an example, a tap type can determinedbased upon a location of a tap on the housing of the client device B104. By way of another example, a combination of a location on thehousing of the client device A 102 and a location on the housing of theclient device B 104 of a tap can correspond to a particular tap type.

It is further contemplated that the example set forth in FIG. 6 can beextended to a scenario where the client device A 102 and the clientdevice B 104 are moved relative to each other within proximity (e.g.,without tapping). For instance, the client device B 104 can move withinproximity of the location 600 or the location 602; thus, relativemovement towards the location 600 can be distinguished from relativemovement towards the location 602, which can enable determining acorresponding gesture type of the relative movement.

FIGS. 7-8 illustrate an example where a tap type is determined basedupon an orientation of the client device A 102 relative to the clientdevice B 104 during the physical gesture (e.g., the tap). As illustratedin FIG. 7, the client device A 102 and the client device B 104 can facea common direction when tapped together. For instance, a back of theclient device A 102 can be tapped to a front of the client device B 104.In contrast, as illustrated in FIG. 8, the client device A 102 and theclient device B 104 can be oriented in opposite directions. Forinstance, as shown in FIG. 8, a back of the client device A 102 can betapped to a back of the client device B 104. According to anotherexample, a front of the client device A 102 can be tapped to a front ofthe client device B 104. Hence, the relative orientations of the clientdevice A 102 and the client device B 104 in the examples of FIGS. 7-8correspond to differing tap types.

Pursuant to another example, it is contemplated that the physicalgesture can be motion of the client device A 102 and the client device B104 relative to each other (e.g., without tapping). Again, theorientations depicted in FIGS. 7-8 can pertain to different gesturetypes when the client device A 102 and the client device B 104 movewithin proximity.

With reference to FIG. 9, illustrated is a system 900 that routes a callto the client device B 104 responsive to a physical gesture between theclient device B 104 and the client device A 102. The system 900 includesa network 902, which further includes a switching center 904. Forexample, the network 902 can include the public switched telephonenetwork (PSTN) (or a portion thereof), and the switching center 904 canbe a telephone switch, the network 902 can be a local network (or aportion thereof) and the switching center 904 can be a private branchexchange (PBX), a combination thereof, or the like.

Following the ongoing example set forth herein, the client device A 102participates in the call and the client device B 104 does notparticipate in the call prior to detection of a physical gesture by thesensing component 110. The access instigation component 112 of theclient device A 102 can initiate the participation of the client deviceB 104 in the call by transmitting a signal over the network 902 to theswitching center 904 from the client device A 102. Thus, the signal canbe sent by the access instigation component 112 to the switching center904 through the telephony system (e.g., the network 902) to requesttransfer to the client device B 104.

Moreover, the signal can cause the switching center 904 to route thecall to the client device B 104. In response to receipt of the signal,the switching center 904 (or a disparate node of the network 902) cancause the client device B 104 to join the call, ring, or the like.According to an example, the switching center 904 can route the call tothe client device B 104 while also routing the call to the client deviceA 102 responsive to receipt of the signal. According to another example,the switching center 904 can discontinue routing the call to the clientdevice A 102 while routing the call to the client device B 104responsive to receipt of the signal.

Turning to FIG. 10, illustrated is another exemplary system 1000 thatemploys physical gestures to initiate transferring calls between clientdevices. The system 1000 includes the client device A 102 and the clientdevice B 104. Moreover, the system 1000 includes a call server 1002(e.g., a Voice over Internet Protocol (VoIP) server). It is contemplatedthat the call server 1002 can be a cloud based communication device, acommunication device (e.g., router, gateway, etc.) on a local network,or the like.

In the example of FIG. 10, the sensing component 110 can detect aphysical gesture (e.g., tap, disparate type of physical gesture, etc.)between the client device A 102 and the client device B 104. Responsiveto detection of the physical gesture, the access instigation component112 can initiate the participation of the client device B 104 in thecall by transmitting a request to the call server 1002 from the clientdevice A 102. The request can cause the call server 1002 to route thecall to the client device B 104. For instance, the request can specifyan IP address of the client device B 104 to which the call is requestedto be routed. Responsive to receipt of the request, the call server 1002can route the call to the client device B 104 (e.g., while also routingthe call to the client device A 102 or without routing the call to theclient device A 102).

With reference to FIG. 11, illustrated is another exemplary system 1100that transfers calls responsive to detected physical gestures betweenclient devices. Again, the system 1100 includes the client device A 102,the client device B 104, and the call server 1002. In the example ofFIG. 11, the sensing component 110 of the client device A 102 can detectthe physical gesture between the client device B 104 and the clientdevice A 102. Moreover, responsive to the detection of the physicalgesture by the sensing component 110, the access instigation component112 can initiate participation of the client device B 104 in the callfrom the client device A 102 by transmitting call access information tothe client device B 104. The client device B 104 can receive the callaccess information and can utilize the call access information toconnect to the call. For instance, the client device B 104 can send arequest to the call server 102, where the request can cause the callserver 1002 to route the call to the client device B 104.

According to the example set forth in FIG. 11, the client device A 102can transmit the call access information over NFC, Wi-Fi, Bluetooth,etc. to the client device B 104. The call access information, forinstance, can include a link or other information informing the clientdevice B 104 how to join the call. According to another example, thecall access information can enable the client device B 104 toautomatically join the call; yet, the claimed subject matter is not solimited. According to another example, it is contemplated that the callaccess information can be a link for a teleconference from aninvitation. According to another example, the call access informationcan be dynamically created by the access instigation component 112 onthe client device A 102 and can be utilized by the client device B 104to join the call. Further, it is contemplated that the call accessinformation can be dynamically generated by the call server 1002, andthereafter, provided to the client device B 104 (e.g., directly from thecall server 1002 to the client device B 104, via the client device A102, etc.).

According to various embodiments, the physical gesture need not contactsomething on the other client device (e.g., the client device B 104 neednot contact the client device A 102). For instance, the client device B104 can be tapped on a table which is registered as a hard stop by anengine included in the client device B 104, which can determine that theclient device B 104 would like to join the call 106. The client device B104 can then connect to the call server 1002 and attempt to join thecall in progress (e.g., by sending the request).

With reference to FIG. 12, illustrated is a system 1200 that sources acall from the client device A 102 to the client device B 104 responsiveto detection of a physical gesture. Again, the client device A 102participates in the call via the first connection. For instance, theclient device A 102 can exchange packets, signals, data, information,etc. pertaining to the call over a network 1202.

Moreover, the sensing component 110 can detect the physical gesturebetween the client device B 104 and the client device A 102 (e.g., whilethe client device A 102 participates in the call and while the clientdevice B 104 is not participating in the call). The client device A 102further includes a routing component 1204 that can source the call tothe client device B 104. Accordingly, the access instigation component112 can cause the client device B 104 to participate in the callresponsive to detection of the physical gesture by enabling the routingcomponent 1204 to send and/or receive packets, signals, data,information, etc. associated with the call to the client device B 104(e.g., the routing component 1204 can source the call to the clientdevice B 104 from the client device A 102). The routing component 1204can source the call over Wi-Fi, Bluetooth, or the like. For instance,following the example of FIG. 12, the client device A 102 can act as aVoIP server to the client device B 104; yet, the claimed subject matteris not so limited.

Turning now to FIG. 13, illustrated is a system 1300 that transferscalls responsive to a physical gesture based upon capabilities of theclient device A 102 and the client device B 104. Again, the clientdevice A 102 can include the communication component 108, the sensingcomponent 110, and the access instigation component 112. Moreover, theclient device A 102 can include a discovery component 1302 that candiscover capabilities of the client device B 104. The discoverycomponent 1302 can further select a communication technique based uponthe capabilities of the client device B 104. Further, the accessinstigation component 112 can initiate the participation of the clientdevice B 104 in the call from the client device A 102 utilizing theconnection technique selected based upon the capabilities of the clientdevice B 104 identified by the discovery component 1302.

Now turning to FIG. 14, illustrated is a system 1400 that routes a callto client device(s) from the call server 1002. The system 1400 includesthe client device A 102 and the client device B 104. The call server1002 can include an interface component 1402 that can transmit datapackets that are part of the call to the client device A 102. Moreover,the interface component 1402 can receive a request to route the datapackets that are part of the call to the client device B 104. Therequest can be received from the client device A 102 and/or the clientdevice B 104 responsive to a detected physical gesture between theclient device A 102 and the client device B 104. Moreover, the datapackets that are part of the call are not routed to the client device B104 prior to receipt of the request by the interface component 1402.

The call server 1002 further includes a connection management component1404 that can determine whether to grant the request or deny therequest. For instance, the connection management component 1404 cangrant or deny the request based upon information included in the request(e.g., specification of a type of physical gesture detected between theclient device A 102 and the client device B 104, identity of the clientdevice A 102, identity of the client device B 104, etc.). Additionallyor alternatively, the connection management component 1404 can determinewhether to grant the request or deny the request utilizing a predefinedpolicy based upon conditions of the call, the client device A 102,and/or the client device B 104. Moreover, the connection managementcomponent 1404 can evaluate whether to grant the request or deny therequest based upon permissions (e.g., an originator of a meeting canspecify that an invitee can pick up the meeting on his client devicefrom a conference phone whereas someone not invited is unable to pick upthe meeting, etc.).

The client device A 102 can further include a control component 1406that can set the predefined policy for granting or denying requests.Although not shown, it is to be appreciated that the control component1406 can be included in the client device B 104, or substantially anyother device (not shown) in the system 1400. The control component 1406can set the predefined policy to grant or deny requests based onconditions such as, location, type of device, identity of device,whether the device is domain joined, etc. For instance, the controlcomponent 1406 can set the predefined policy generally for the clientdevice A 102, for a given meeting (e.g., setting on a meetinginvitation, etc.), or the like.

Moreover, the connection management component 1404 of the call server1002 can determine whether to continue to transmit the data packets thatare part of the call to the client device A 102 or discontinuetransmission of the data packets that are part of the call to the clientdevice A 102 based at least in part upon request. Responsive to thedetermination to grant the request to transmit the data packets to theclient device B 104, the interface component 1402 can then eithercontinue to transmit the data packets that are part of the call to theclient device A 102 or discontinue the transmission of the data packetsthat are part of the call to the client device A 102. Again, the controlcomponent 1406 can set the predefined policy, which can specify whetherto continue or discontinue transmission of the data packets that arepart of the call to the client device A 102, based on conditions suchas, location, type of device, identity of device, whether the device isdomain joined, etc; further, the connection management component 1404can determine whether to continue or discontinue such transmission basedupon the predefined policy.

Turning to FIG. 15, illustrated is a system 1500 that employs agentswith the client devices (e.g., agents of client devices that perform thecommunications of a call). According to the example shown, the clientdevice A 102 can be associated with an agent 1502 and the client deviceB 104 can be associated with an agent 1504. It is to be appreciated thatthe client device A 102 can be associated with substantially any numberof agents substantially similar to the agent 1502 and/or the clientdevice B 104 can be associated with substantially any number of agentssubstantially similar to the agent 1504.

Substantially any type of agent of a client device is intended to fallwithin the scope of the hereto appended claims. Examples of types ofagents include devices coupled with a client device (e.g., a Bluetoothearpiece, etc.), a display screen of a client device, a keyboard of aclient device, a sensor associated with a client device (e.g., a camera,etc.), a table on which a conference phone is situated, a portion of acar (e.g., dashboard, door, steering wheel, etc.) where the car includesan integrated phone, or the like.

The examples described herein can be extended to scenarios that includeagents (e.g., the agent 1502, the agent 1504, etc.). For instance, aphysical gesture (e.g., tapping) can be utilized to enable or disableagents of client devices (e.g., Bluetooth earpieces, etc.). Accordingly,a physical gesture can be detected between the agent 1502 (of the firstclient device A 102) and the client device B 104. According to anotherexample, a physical gesture can be detected between the agent 1504 (ofthe client device B 104) and the client device A 102. By way of yetanother example, a physical gesture can be detected between the agent1502 (of the client device A 102) and the agent 1504 (of the clientdevice B 104).

Turning to FIG. 16, illustrated is a system 1600 that employs a sensor1602 (e.g., a disparate client-side device) to detect the physicalgesture between the client device A 102 and the client device B 104. Thesensor 1602 can include a sensing component 1604, which can besubstantially similar to the sensing component 110 of FIG. 1. It is tobe appreciated that the sensor 1602 can be coupled with the clientdevice A 102 and/or the client device B 104.

For example, the sensor 1602 can be a camera. Following this example,the sensor 1602 can be a camera in a conference room, for instance.Accordingly, the camera can detect a physical gesture of the clientdevice B 104, which can be signaled to the client device A 102.Thereafter, the access instigation component 112 of the client device A102 can initiate participation of the client device B 104 in the callfrom the client device A 102 responsive to the detection of the physicalgesture. Yet, it is contemplated that the claimed subject matter is notlimited to the foregoing. Pursuant to another example, it iscontemplated that the sensor 1602 can include the access instigationcomponent 112; yet, the claimed subject matter is not so limited.

Various exemplary scenarios can be implemented utilizing the techniquesdescribed herein. It is to be appreciated that the following scenariosare presented for illustration purposes, and the claimed subject matteris not limited to the following scenarios.

According to an exemplary scenario, a user can be in a conference callin a conference room. The conversation can be ongoing when the roombooking ends. Accordingly, the user can tap his mobile device to aconference phone in the conference room. When the user taps his mobiledevice to the conference phone, a screen can be displayed (e.g., on adisplay screen associated with the conference phone, on a display screenof the mobile device of the user, etc.) with a message that offers anoption to take the conference call, join the conference call, or cancel.The user can take the conference call and the conference phone in theconference room can discontinue participating in the conference call.The user can thereafter continue participating in the conference call inthe hall with his mobile device, while a next booking can use theconference room.

Pursuant to another exemplary scenario, and again referring to the aboveconference room scenario where the user is participating in theconference call in the hall, another attendee from the conference roomwho desires to join the continuing conference call can tap her mobiledevice to the mobile device of the initial user currently participatingin the conference call. The initial user may or may not have to approvethe inclusion of the subsequent user to the conference call. Thus, twoattendees of the conference call can continue to participate in theconference call (e.g., while walking separate directions, etc.).

Moreover, one of the users from the foregoing conference room scenariocan return to his or her office. Following this exemplary scenario, themobile device participating in the conference call can be tapped to aphone (e.g., VoIP phone) in his or her office, and an accept button onthe office phone can be selected. Thereafter, the user can disconnectthe mobile device from the conference call. Thus, the office phone canbe joined to the conference call, and the user can continue toparticipate in the conference call through the office phone.

In accordance with another exemplary scenario, a car of a user caninclude an in-vehicle communications and infotainment system, which canbe participating in an active call while the car is parked (e.g., thein-vehicle communications and infotainment system participates in thecall without participation of a separate phone). The user can have twoBluetooth devices (e.g., agents) in the car, one headset and one phone.It can be ambiguous which device plays the audio and which microphonepicks up the voice subsequent to transfer. The in-vehicle communicationsand infotainment system can identify that the phone is the source of thecommunication. Before the leaving the car, the user can tap theBluetooth headset to the car. Thereafter, the car can transfer the callto the phone while activating the connection through the Bluetoothheadset, allowing the headset to be activate when the car is turned off.

FIGS. 17-19 illustrate exemplary methodologies relating to initiation ofa transfer of a call or a conference call between client devicesresponsive to detection of a physical gesture. While the methodologiesare shown and described as being a series of acts that are performed ina sequence, it is to be understood and appreciated that themethodologies are not limited by the order of the sequence. For example,some acts can occur in a different order than what is described herein.In addition, an act can occur concurrently with another act. Further, insome instances, not all acts may be required to implement a methodologydescribed herein.

Moreover, the acts described herein may be computer-executableinstructions that can be implemented by one or more processors and/orstored on a computer-readable medium or media. The computer-executableinstructions can include a routine, a sub-routine, programs, a thread ofexecution, and/or the like. Still further, results of acts of themethodologies can be stored in a computer-readable medium, displayed ona display device, and/or the like.

FIG. 17 illustrates a methodology 1700 of joining a client device to anexisting call. At 1702, a physical gesture between a first client deviceand a second client device can be detected. The first client device isparticipating in a call at the time of detection of the physicalgesture. Moreover, the second client device is not participating in thecall at the time of the detection of the physical gesture. At 1704,responsive to the detection of the physical gesture, participation ofthe second client device in the call can be initiated.

According to an example, the physical gesture between the first clientdevice and the second client device can be detected utilizing the firstclient device. Following this example, participation of the secondclient device in the call can be initiated from the first client deviceresponsive to the detection of the physical gesture.

Pursuant to another example, the physical gesture between the firstclient device and the second client device can be detected utilizing thesecond client device. Accordingly, participation of the second clientdevice in the call can be initiated from the second client deviceresponsive to the detection of the physical gesture.

In accordance with yet another example, the physical gesture between thefirst client device and the second client device can be detected by adisparate client-side device (e.g., a sensor). Following this example,participation of the second client device in the call can be initiatedfrom the disparate client-side device, the first client device, thesecond client device, a server, or the like responsive to the detectionof the physical gesture.

By way of yet another example, the physical gesture between the firstclient device and the second client device can be detected by a server.In accordance with such example, participation of the second clientdevice in the call can be initiated from the server responsive to thedetection of the physical gesture.

Now turning to FIG. 18, illustrated is a methodology 1800 of routing acall. At 1802, data packets that are part of the call can be transmittedto a first client device. At 1804, a request to route the data packetsthat are part of the call to a second client device can be received. Therequest can be responsive to a detected physical gesture between thefirst client device and the second client device. The request can bereceived, for example, from the first client device, the second clientdevice, a disparate server, or the like. Moreover, the data packets thatare part of the call are not routed to the second client device prior toreceipt of the request.

At 1806, a determination can be made concerning whether to grant therequest or deny the request. If the request is granted at 1806, then themethodology 1800 can continue to 1808. At 1808, the data packets thatare part of the call can be transmitted to the second client device.Alternatively, if the request is denied at 1806, then the methodology1800 can end (e.g., the data packets that are part of the call are nottransmitted to the second client device responsive to the request).

With reference to FIG. 19, illustrated is another exemplary methodology1900 of routing a call. At 1902, data packets that are part of the callcan be transmitted to a first client device. At 1904, a request to routethe data packets that are part of the call to a second client device canbe received. At 1906, a determination can be made concerning whether togrant the request or deny the request. If the request is denied at 1906,then the methodology 1900 ends (e.g., the data packets that are part ofthe call are not transmitted to the second client device responsive tothe request). If the request is granted at 1906, then the methodologycan continue to 1908.

At 1908, a determination can be made concerning whether to continue ordiscontinue transmission to the first client device. Responsive to adetermination to continue to transmit to the first client device at1908, the methodology 1900 can continue to 1910. At 1910, the datapackets that are part of the call can be transmitted to the first clientdevice and the second client device.

Alternatively, if a determination is made to discontinue thetransmission to the first client device at 1908, then the methodology1900 can continue to 1912. At 1912, the data packets that are part ofthe call can be transmitted to the second client device. At 1914,transmission of the data packets that are part of the call can bediscontinued to the first client device.

Referring now to FIG. 20, a high-level illustration of an exemplarycomputing device 2000 that can be used in accordance with the systemsand methodologies disclosed herein is illustrated. For instance, thecomputing device 2000 may be a client device (e.g., the client device A102, the client device B 104, etc.). By way of another example, thecomputing device 2000 may be a call server (e.g., the call server 1002).The computing device 2000 includes at least one processor 2002 thatexecutes instructions that are stored in a memory 2004. The instructionsmay be, for instance, instructions for implementing functionalitydescribed as being carried out by one or more components discussed aboveor instructions for implementing one or more of the methods describedabove. The processor 2002 may access the memory 2004 by way of a systembus 2006. In addition to storing executable instructions, the memory2004 may also store identifiers, data pertaining to calls, call accessinformation, and so forth.

The computing device 2000 additionally includes a data store 2008 thatis accessible by the processor 2002 by way of the system bus 2006. Thedata store 2008 may include executable instructions, identifiers, datapertaining to calls, call access information, etc. The computing device2000 also includes an input interface 2010 that allows external devicesto communicate with the computing device 2000. For instance, the inputinterface 2010 may be used to receive instructions from an externalcomputer device, from a user, etc. The computing device 2000 alsoincludes an output interface 2012 that interfaces the computing device2000 with one or more external devices. For example, the computingdevice 2000 may display text, images, etc. by way of the outputinterface 2012.

It is contemplated that the external devices that communicate with thecomputing device 2000 via the input interface 2010 and the outputinterface 2012 can be included in an environment that providessubstantially any type of user interface with which a user can interact.Examples of user interface types include graphical user interfaces,natural user interfaces, and so forth. For instance, a graphical userinterface may accept input from a user employing input device(s) such asa keyboard, mouse, remote control, or the like and provide output on anoutput device such as a display. Further, a natural user interface mayenable a user to interact with the computing device 2000 in a mannerfree from constraints imposed by input device such as keyboards, mice,remote controls, and the like. Rather, a natural user interface can relyon speech recognition, touch and stylus recognition, gesture recognitionboth on screen and adjacent to the screen, air gestures, head and eyetracking, voice and speech, vision, touch, gestures, machineintelligence, and so forth.

Additionally, while illustrated as a single system, it is to beunderstood that the computing device 2000 may be a distributed system.Thus, for instance, several devices may be in communication by way of anetwork connection and may collectively perform tasks described as beingperformed by the computing device 2000.

As used herein, the terms “component” and “system” are intended toencompass computer-readable data storage that is configured withcomputer-executable instructions that cause certain functionality to beperformed when executed by a processor. The computer-executableinstructions may include a routine, a function, or the like. It is alsoto be understood that a component or system may be localized on a singledevice or distributed across several devices.

Further, as used herein, the term “exemplary” is intended to mean“serving as an illustration or example of something.”

Various functions described herein can be implemented in hardware,software, or any combination thereof. If implemented in software, thefunctions can be stored on or transmitted over as one or moreinstructions or code on a computer-readable medium. Computer-readablemedia includes computer-readable storage media. A computer-readablestorage media can be any available storage media that can be accessed bya computer. By way of example, and not limitation, suchcomputer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM orother optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium that can be used to carry or storedesired program code in the form of instructions or data structures andthat can be accessed by a computer. Disk and disc, as used herein,include compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk, and blu-ray disc (BD), where disks usuallyreproduce data magnetically and discs usually reproduce data opticallywith lasers. Further, a propagated signal is not included within thescope of computer-readable storage media. Computer-readable media alsoincludes communication media including any medium that facilitatestransfer of a computer program from one place to another. A connection,for instance, can be a communication medium. For example, if thesoftware is transmitted from a website, server, or other remote sourceusing a coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave, then the coaxial cable, fiber optic cable, twisted pair,DSL, or wireless technologies such as infrared, radio and microwave areincluded in the definition of communication medium. Combinations of theabove should also be included within the scope of computer-readablemedia.

Alternatively, or in addition, the functionality described herein can beperformed, at least in part, by one or more hardware logic components.For example, and without limitation, illustrative types of hardwarelogic components that can be used include Field-programmable Gate Arrays(FPGAs), Program-specific Integrated Circuits (ASICs), Program-specificStandard Products (ASSPs), System-on-a-chip systems (SOCs), ComplexProgrammable Logic Devices (CPLDs), etc.

What has been described above includes examples of one or moreembodiments. It is, of course, not possible to describe everyconceivable modification and alteration of the above devices ormethodologies for purposes of describing the aforementioned aspects, butone of ordinary skill in the art can recognize that many furthermodifications and permutations of various aspects are possible.Accordingly, the described aspects are intended to embrace all suchalterations, modifications, and variations that fall within the spiritand scope of the appended claims. Furthermore, to the extent that theterm “includes” is used in either the details description or the claims,such term is intended to be inclusive in a manner similar to the term“comprising” as “comprising” is interpreted when employed as atransitional word in a claim.

What is claimed is:
 1. A method of joining a client device to anexisting call, comprising: detecting a physical gesture between a firstclient device a second client device, wherein the first client device isparticipating in a call at a time of detection of the physical gesture,and wherein the second client device is not participating in the call atthe time of the detection of the physical gesture; and responsive to thedetection of the physical gesture, initiating participation of thesecond client device in the call, wherein initiation of theparticipation of the second client device in the call enables the secondclient device to be used by a user to participate in the call.
 2. Themethod of claim 1, wherein initiating the participation of the secondclient device in the call further comprises causing the call to transferfrom the first client device to the second client device.
 3. The methodof claim 1, wherein initiating the participation of the second clientdevice in the call further comprises causing the second client device tojoin the call while the first client device continues to participate inthe call.
 4. The method of claim 1, further comprising, responsive tothe participation of the second client device in the call beinginitiated, sourcing the call to the second client device from the firstclient device.
 5. The method of claim 1, wherein initiating theparticipation of the second client device in the call further comprisestransmitting a request to a server from the first client device, whereinthe request causes the server to route the call to the second clientdevice.
 6. The method of claim 1, wherein initiating the participationof the second client device in the call further comprises transmitting asignal to a switching center from the first client device, wherein thesignal causes the switching center to route the call to the secondclient device.
 7. The method of claim 1, wherein initiating theparticipation of the second client device in the call further comprisestransmitting call access information to the second client device,wherein the second client device employs the call access information toconnect to the call.
 8. The method of claim 1, wherein the physicalgesture comprises a tap between the second client device and the firstclient device.
 9. The method of claim 1, wherein the physical gesturecomprises at least one of: a tap between an agent of the first clientdevice and the second client device; a tap between the first clientdevice and an agent of the second client device; or a tap between theagent of the first client device and the agent of the second clientdevice.
 10. The method of claim 1, further comprising: identifying agesture type of the physical gesture from a set of possible gesturetypes, wherein the possible gesture types in the set correspond todiffering respective actions pertaining to the call; and causing aparticular action pertaining to the call corresponding to the gesturetype responsive to the detection of the physical gesture andidentification of the gesture type.
 11. The method of claim 10, furthercomprising identifying the gesture type of the physical gesture as afunction of at least one of a location on a housing at which thephysical gesture is detected, a duration of the physical gesture, or anumber of occurrences of the physical gesture.
 12. The method of claim1, further comprising: discovering capabilities of the second clientdevice; selecting a connection technique based upon the capabilities ofthe second client device; and initiating the participation of the secondclient device in the call utilizing the connection technique selectedbased upon the capabilities of the second client device.
 13. The methodof claim 1, further comprising discerning an identifier of the secondclient device when the physical gesture between the second client deviceand the first client device is detected, wherein the identifier isutilized to initiate the participation of the second client device inthe call.
 14. A client device, comprising: a sensing componentconfigured to detect a tap between the client device and a disparateclient device, wherein the client device is participating in a call at atime of detection of the tap, and wherein the disparate client device isnot participating in the call at the time of the detection of the tap;and an access instigation component configured to initiate participationof the disparate client device in the call responsive to the detectionof the tap between the client device and the disparate client device,wherein initiation of the participation of the disparate client devicein the call enables the disparate client device to be used by a user toparticipate in the call.
 15. The client device of claim 14, furthercomprising a type evaluation component configured to identify a tap typeof the tap from a set of possible tap types, wherein the possible taptypes in the set correspond to differing respective actions pertainingto the call, and the access instigation component being furtherconfigured to cause a particular action pertaining to the callcorresponding to the tap type responsive to the detection of the tap andidentification of the tap type.
 16. The client device of claim 15,wherein a first possible tap type corresponds to a transfer action wherethe call is transferred from the client device to the disparate clientdevice, and wherein a second possible tap type corresponds to aconference action where the disparate client device is joined to thecall while the client device continues to participate in the call. 17.The client device of claim 15, the type evaluation component beingfurther configured to identify the tap type of the tap as a function ofat least one of a location on a housing of the client device at whichthe tap is detected, an orientation of the disparate client device withrespect to the client device during the tap, a time duration of the tap,or a number of occurrences of the tap.
 18. The client device of claim14, the access instigation component being further configured totransmit a request to a server from the client device responsive to thedetection of the tap between the client device and the disparate clientdevice, wherein the request causes the server to route the call to thesecond client device.
 19. A conference phone, comprising: a sensingcomponent configured to detect a tap of a mobile device to theconference phone, wherein the conference phone is participating in acall at a time of detection of the tap, and wherein the mobile device isnot participating in the call at the time of the detection of the tap;and an access instigation component configured to initiate participationof the mobile device in the call responsive to the detection of the tapof the mobile device to the conference phone, wherein initiation of theparticipation of the mobile device in the call enables the mobile deviceto be used by a user to participate in the call.
 20. The conferencephone of claim 19, further comprising: a display screen configured todisplay a prompt to transfer the call to the mobile device and a promptto join the mobile device to the call responsive to the detection of thetap of the mobile device to the conference phone; and the accessinstigation component further being configured to one of transfer thecall to the mobile device or join the mobile device to the callresponsive to user input concerning whether to transfer the call to themobile device or join the mobile device to the call.